System and method for event based internet of things (iot) device status monitoring and reporting in a mobility network

ABSTRACT

Protocol agnostic wrapping (PAW) and/or data analytics engine (DAE) functions are embedded within a service capability exposure function (SCEF) entity for handling dynamic device triggering, event monitoring, and/or reporting of Internet of things (IoT) devices. The enhanced SCEF creates a dynamic mobility network infrastructure model for global IoT connectivity and new services delivery. The PAW function can be utilized for enhancing massive IoT devices connectivity with their respective application servers in the next-generation mobility network. By employing the PAW function, the SCEF can generate and securely expose flexible application programming interfaces (APIs) to the external network of various third party IoT application service providers, which in turn can utilize the APIs to access their targeted IoT devices via network elements and extract critical device and network capabilities on an event basis.

RELATED APPLICATION

The subject patent application is a continuation of, and claims priorityto, U.S. patent application Ser. No. 15/169,699, filed May 31, 2016 andentitled “SYSTEM AND METHOD FOR EVENT BASED INTERNET OF THINGS (IOT)DEVICE STATUS MONITORING AND REPORTING IN A MOBILITY NETWORK,” theentirety of which application is hereby incorporated by referenceherein.

TECHNICAL FIELD

The subject disclosure relates to wireless communications, e.g., asystem and method for event based Internet of things (IoT) device statusmonitoring and reporting in a mobility network.

BACKGROUND

The Internet of Things (IoT) holds a great promise for the future of theglobal communications industry. The connectivity of humans and machines(e.g., smart phones, tablet computers, home appliances, etc.) viahigh-speed mobile internet technologies such as Long Term Evolution(LTE), LTE-Advanced (LTE-A) and its evolution, forms the basis for asuccessful global IoT implementation. As the number of connected devicesthat are capable of establishing connectivity with other devices and/orpassive objects to exchange data continues to rise steadily, the IoTtechnology gains widespread proliferation in the information technologyindustry. IoT enables creation of an information-rich eco-system thatcan enrich modern connected way of life and transform the way in whichbusinesses as well as consumers function today.

With the advent of several new competing wireless technologies, globaloperators as well as third party application/service providers aredriving to enhance the mobile IoT devices connectivity model utilizingcomplementary radio access schemes and efficiently transporting theresulting digitized data via a suitable core transport networking gear.The number of such autonomous connected “things” is expected to grow to20+ billion by 2020, per Global Industry Analyst's reports.

The ability to connect mobile IoT devices across various industryverticals with traditional smartphones, humans, and other key passiveobjects over Internet, as well as collect and analyze the raw dataproduced by an eco-system of such IoT devices, and transform theresulting raw data into usable information makes IoT the next majortechnology disruptor in creating a truly globally connected world. Suchan ability to connect massive number of IoT devices creates newchallenges for the networking infrastructure providers to developinnovative and intelligent networking solutions that can deliver optimalconnectivity as well as end user service quality.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example system that facilitates event-basedInternet of things (IoT) device status monitoring and/or reporting.

FIG. 2 illustrates an example system for dynamic application programminginterface (API) exposure in a pooled configuration.

FIG. 3 illustrates an example system for a policy-based dedicatedinterface to API exchange associated with control-plane entitiesdeployed in a pooled configuration.

FIG. 4 illustrates an example system for providing redundancy duringpolicy-based API generation.

FIG. 5 illustrates an example system that facilitates routing of IoTroaming traffic via service capability exposure function (SCEF)interworking.

FIG. 6 illustrates an example system that comprises a SCEF integratedwith a data analytics engine (DAE).

FIG. 7 illustrates an example system that facilitates automating one ormore features in accordance with the subject embodiments.

FIG. 8 illustrates an example method that facilitates protocol agnosticwrapping of traffic associated with IoT devices during API generation.

FIG. 9 illustrates an example method that facilitates integrating dataanalytics capabilities in a SCEF

FIG. 10 illustrates a Long Term Evolution (LTE) network architecturethat can employ the disclosed architecture.

FIG. 11 illustrates a block diagram of a computer operable to executethe disclosed communication architecture.

FIG. 12 illustrates a schematic block diagram of a computing environmentin accordance with the subject specification.

DETAILED DESCRIPTION

One or more embodiments are now described with reference to thedrawings, wherein like reference numerals are used to refer to likeelements throughout. In the following description, for purposes ofexplanation, numerous specific details are set forth in order to providea thorough understanding of the various embodiments. It may be evident,however, that the various embodiments can be practiced without thesespecific details, e.g., without applying to any particular networkedenvironment or standard. In other instances, well-known structures anddevices are shown in block diagram form in order to facilitatedescribing the embodiments in additional detail.

As used in this application, the terms “component,” “module,” “system,”“interface,” “node,” “platform,” “server,” “controller,” “entity,”“element,” “gateway,” “engine,” or the like are generally intended torefer to a computer-related entity, either hardware, a combination ofhardware and software, software, or software in execution or an entityrelated to an operational machine with one or more specificfunctionalities. For example, a component may be, but is not limited tobeing, a process running on a processor, a processor, an object, anexecutable, a thread of execution, computer-executable instruction(s), aprogram, and/or a computer. By way of illustration, both an applicationrunning on a controller and the controller can be a component. One ormore components may reside within a process and/or thread of executionand a component may be localized on one computer and/or distributedbetween two or more computers. As another example, an interface cancomprise input/output (I/O) components as well as associated processor,application, and/or API components.

Further, the various embodiments can be implemented as a method,apparatus, or article of manufacture using standard programming and/orengineering techniques to produce software, firmware, hardware, or anycombination thereof to control a computer to implement one or moreaspects of the disclosed subject matter. An article of manufacture canencompass a computer program accessible from any computer-readabledevice or computer-readable storage/communications media. For example,computer readable storage media can comprise but are not limited tomagnetic storage devices (e.g., hard disk, floppy disk, magnetic strips. . . ), optical disks (e.g., compact disk (CD), digital versatile disk(DVD) . . . ), smart cards, and flash memory devices (e.g., card, stick,key drive . . . ). Of course, those skilled in the art will recognizemany modifications can be made to this configuration without departingfrom the scope or spirit of the various embodiments.

In addition, the word “example” or “exemplary” is used herein to meanserving as an example, instance, or illustration. Any aspect or designdescribed herein as “exemplary” is not necessarily to be construed aspreferred or advantageous over other aspects or designs. Rather, use ofthe word exemplary is intended to present concepts in a concretefashion. As used in this application, the term “or” is intended to meanan inclusive “or” rather than an exclusive “or.” That is, unlessspecified otherwise, or clear from context, “X employs A or B” isintended to mean any of the natural inclusive permutations. That is, ifX employs A; X employs B; or X employs both A and B, then “X employs Aor B” is satisfied under any of the foregoing instances. In addition,the articles “a” and “an” as used in this application and the appendedclaims should generally be construed to mean “one or more” unlessspecified otherwise or clear from context to be directed to a singularform.

Moreover, terms like “user equipment,” “communication device,” “mobiledevice,” “mobile station,” and similar terminology, refer to a wired orwireless communication-capable device utilized by a subscriber or userof a wired or wireless communication service to receive or convey data,control, voice, video, sound, gaming, or substantially any data-streamor signaling-stream. The foregoing terms are utilized interchangeably inthe subject specification and related drawings. Data and signalingstreams can be packetized or frame-based flows. Further, the terms“user,” “subscriber,” “consumer,” “customer,” and the like are employedinterchangeably throughout the subject specification, unless contextwarrants particular distinction(s) among the terms. It should be notedthat such terms can refer to human entities or automated componentssupported through artificial intelligence (e.g., a capacity to makeinference based on complex mathematical formalisms), which can providesimulated vision, sound recognition and so forth. Further, it is notedthat the term “downstream” as used herein refers to a direction in whichdata sent for a “stream” flowing from a network service provider device(or content provider device or application provider device) to a userdevice. As an example, if a first device is closer to (fewer hops awayfrom) the network service provider device than a second device, then thefirst device is said to be upstream from the second device orconversely, the second device is downstream from the first device.

Aspects or features of the disclosed subject matter can be exploited insubstantially any wired or wireless communication technology; e.g.,Universal Mobile Telecommunications System (UMTS), Wi-Fi, WorldwideInteroperability for Microwave Access (WiMAX), General Packet RadioService (GPRS), Enhanced GPRS, Third Generation Partnership Project(3GPP) Long Term Evolution (LTE), Third Generation Partnership Project 2(3GPP2) Ultra Mobile Broadband (UMB), High Speed Packet Access (HSPA),Zigbee, or another IEEE 802.XX technology, Fifth generation (5G), etc.Additionally, substantially all aspects of the disclosed subject mattercan be exploited in legacy (e.g., wireline) telecommunicationtechnologies.

As the number of connected devices that are capable of establishingconnectivity with other devices and/or passive objects to exchange datacontinues to rise steadily over the high-speed mobile Internet, theInternet of Things (IoT) technology gains widespread proliferation inthe information technology industry. IoT, which is the future ofinternet connectivity, enables creation of an information richeco-system that can enrich modern connected way of life and transformthe way in which businesses as well as consumers function today.

With the advent of several new competing wireless technologies such asSIGFOX/LoRa wide area network (WAN)™/Low-Power, Wide-Area (LPWA)/NarrowBand cellular IoT/enhanced machine type communication (eMTC), etc.,global operators as well as third party application/service providersare driving to enhance the mobile IoT devices connectivity modelutilizing such complementary radio access schemes and efficientlytransport the resulting digitized data via a suitable core transportnetworking gear. The systems and methods disclosed herein provideefficient control plane based device triggering, monitoring, and/ormessage exchange mechanisms to establish high-speed mobile connectivityassociated with such a massive number of IoT devices in an operator'smobility network. Control plane based messages are exchanged overmultiple signaling interfaces, undergoing multiple layers of protocolconversion when interacting with a service capability exposure function(SCEF), depending on the applications, before a request from a thirdparty IoT application server reaches the IoT device and vice-versa. Inone embodiment, a SCEF is disclosed herein that expedites such IoTmessage exchanges by employing a protocol agnostic wrapper (PAW)function. Moreover, the PAW function simplifies the interfaceconnectivity between the various network elements, the SCEF, and anexternal provider's reachability model, thereby facilitating rapid anddirect access to the network. This direct connectivity approach avoidstraversing through multiple interface protocol conversions between a setof standard network elements and thus minimizes the overall controlplane signaling required to reach the IoT devices. In addition, thewrapper function provides flexibility to expose a configurable andselected set of APIs to the external providers based on one or moreoperator defined service agreements. In one aspect, it is noted that thePAW function wrapper can be a broad protocol to API translation functionand can be independent of underlying access technologies.

Lack of a PAW function within the SCEF to expose a generic set of APIsfor multiple application layer signaling protocols towards the externalproviders results in an inefficient mobility network design and targetednetwork element access that could result in IoT service impacts acrossmultiple service providers. Lack of adequate analytics capabilitieswithin the SCEF on a per protocol conversion per network element willnot adequately expose the services and capabilities of the underlyingnetwork. This can lead to multi-access based mobility core networkarchitectures with critical interworking entities that are notinherently flexible and dynamically reconfigurable to provide specificevent based configuration, monitoring and reporting information aboutthe incumbent IoT devices served by the network provider, thereby notaddressing the demands of service providers. Additionally, this canresult in direct revenue loss for several network operators whichotherwise could have benefited from delivery of new services with theintroduction of new IoT devices into the market.

Referring initially to FIG. 1, there illustrated is an example system100 that facilitates event-based Internet of things (IoT) device statusmonitoring and/or reporting, according to one or more aspects of thedisclosed subject matter. The ability to connect mobile IoT devicesacross various industry verticals with traditional smartphones, humans,and other key passive objects over Internet, as well as collect andanalyze the raw data produced by an eco-system of such IoT devices, andtransform their resulting raw data into usable information makes IoT thenext major technology disruptor in creating a truly globally connectedworld. Such an ability to connect a massive number of IoT devicescreates new challenges for the networking infrastructure providers todevelop innovative and intelligent networking solutions that can deliveroptimal connectivity as well as end user service quality. To overcomethese challenges, system 100 employs a service capability exposurefunction (SCEF) component (referred to herein as SCEF 102) that acts asan IoT gateway and/or proxy to a communication network (e.g., a cellularnetwork).

In one aspect, the SCEF 102 can provide a secure connection betweencontrol plane entity(ies) 104 of the communication network andapplication server(s) (AS(s)) 106. As an example, the AS(s) 106 cancomprise third party IoT service providers such as vertical industry,government, and/or enterprise services, over-the-top content (OTT)providers, and/or other application and/or service providers. As anexample, the control plane entity(ies) 104 can comprise, but are notlimited to, an MME and/or a Serving GPRS Support Node (SGSN), a homesubscriber server (HSS), a policy and charging rules function (PCRF), abroadcast multicast service center (BMSC), a machine typecommunication-interworking function (MTC-IWF), a serving call sessioncontrol function (S-CSCF), a radio access network (RAN) congestionawareness function (RCAF), etc., that are coupled to the SCEF 102 viarespective interfaces (e.g., T6a, T6b, S6t, Rx, Nt, MB2, Tsp, ISC, Ns,etc.). Most often, the interfaces can be specified by industrystandards, for example, 3GPP standards. In one aspect, the SCEF 102securely exposes these interfaces to the AS(s) 106 via appropriate,standardized, and/or reconfigurable application programming interfaces(APIs). Typically, the SCEF 102 can be deployed within the trusteddomain of a network operator of the communication network, while theapplication can belong to the trusted domain or can lie outside thetrust domain.

In some embodiments, the SCEF 102 can abstract services from theunderlying network interfaces and/or protocols and allow the AS(s) 106to access the network infrastructure (or portions of the networkinfrastructure). Accordingly, the AS(s) 106 can target specific servicesto specific set of user equipment (UE) with specific capabilities, forexample, located within a given geographical area. Typically, the UE cancomprise IoT/machine-to-machine (M2M) devices such as, but not limitedto, most any LTE-based appliance, machine, and/or device. As an example,IoT/M2M devices comprise one or more sensors and/or a radio frequencyidentification (RFID) reader, and are typically employed for automateddata transmission and/or measurement between mechanical and/orelectronic devices. However, it is noted that the UE is not limited toan IoT/M2M device and can also comprise most any electroniccommunication device such as, but not limited to, most any consumerelectronic device, for example, a tablet computer, a digital mediaplayer, a digital camera, a cellular phone, a personal computer, apersonal digital assistant (PDA), a smart phone, a laptop, a wearabledevice (e.g., smart watch, connected glasses, wrist monitor, etc.), agaming system, etc. It is noted that the UE can be mobile, have limitedmobility and/or be stationary.

Typically, IoT/M2M devices can have different characteristics thanregular UEs (e.g., non-M2M devices, such as smart phones, tabletcomputers, personal computers, etc.). For example, the IoT/M2M devicesgenerally generate a much greater number of signaling connections in themobile core network as compared to regular UEs. Further, in anotherexample, the service provider often performs simultaneous devicetriggering and monitoring for targeted IoT applications and services.The SCEF 102 can provide various enhancements to conventional entitiesthat expose various network elements using several APIs towards externalservice providers to effectively deal with the IoT/M2M devicescommunication and their eco-system.

In the downstream direction, the SCEF 102 connects with several controlplane network entity(ies) 104 via dedicated signaling interfaces thatcan utilize different application and transport layer protocols. In theupstream direction, the SCEF exposes the control plane networkentity(ies) 104 via a set of standardized and/or customized APIs and/orsecure policies to the external AS(s) 106. According to an aspect, inorder to securely expose a given control plane network entity(ies) 104to the external AS(s) 106 for access, the SCEF 102 can map theunderlying application layer protocol and its detailed systemicattributes into a suitable data set that could be exposed via an API tothe external application processing entity.

If multiple control plane network entity(ies) 104 and their signalinginterfaces are to be exposed via dedicated APIs to an external entity,complexity and inefficiency in conventional SCEF design is significantlyincreased. Moreover, in a large operator environment, there typicallyexist, pools of network elements that deliver mobility functions andservices to a large number (e.g., millions) of users and their devices.IoT traffic adds to the control plane signaling transactions that needto be handled by these standardized network elements across severalsignaling interfaces. Handling individual protocol conversions from eachof the network elements in a given pool as well as across several poolsand exposing them via dedicated APIs to multiple service providers canbe an onerous and inefficient task. In one aspect, the SCEF 102comprises a protocol agnostic wrapping (PAW) component 108 that candynamically handle such massive IoT traffic evolution in an intelligentmanner so that normal mobility services are not impacted.

According to an embodiment, the PAW component 108 provides anintelligent wrapping function that can wrap application layer protocolsassociated with dedicated signaling interfaces to a standardized set ofAPIs that can be interfaced with the external AS(s) 106 to be able togain easy access to the communication network. Moreover, the PAWcomponent 108 can present any interface implemented by the network tothe external AS(s) 106 as a unique and reconfigurable API. As anexample, the external AS(s) 106, by employing the flexible APIs exposedvia the PAW component 108, can communicate with their targeted IoTdevices via specific network elements to extract critical device and/ornetwork capabilities on an event basis. As an example, the extractedinformation can be utilized by the AS(s) 106 to deliver new services tosuch IoT devices on demand. Moreover, the PAW component 108 can performprotocol to API conversion monitoring operations that help in effectiverouting of the bidirectional traffic between a targeted network element(e.g., control plane entity 104) and service providers (e.g., AS 106) togain access to the digitized information associated with desired set ofIoT devices.

Referring now to FIG. 2, there illustrated is an example system 200 fordynamic API exposure in a pooled configuration, in accordance with anaspect of the subject disclosure. It is noted that the SCEF 102, controlplane entity(ies) 104, and AS(s) 106 can comprise functionality as morefully described herein, for example, as described above with regard tosystem 100. Further, although system 200 is described with respect to a3GPP LTE network, it is noted that the subject disclosure is not limitedto 3GPP LTE networks and can be utilized in most any communicationnetwork.

LTE-based IoT devices upon powering up for the first time try to attachto the mobility management entity (MME) 202 in the mobility corenetwork. Once the MME 202 receives such requests for connectionestablishment, it extracts the IoT devices capabilities andauthenticates them with their home subscriber server (HSS) 204, forexample, via routing through diameter routing agents (DRA) using an S6adiameter signaling interface. In doing so, the MME 202 can complete therequired diameter signaling transactions and then accept IoT deviceattachments.

The SCEF 102 adds to the overall mobility core network complexity. Forexample, the SCEF 102 can support several different signaling interfacestowards existing (and/or future) downstream network elements/functions,such as, but not limited to the MME (and/or SGSN) 202, the HSS 204, aBroadcast Multicast Service Center (BMSC) 206, a machine typecommunication interworking function (MTC-IWF) 208, etc. The SCEF 102 canexpose the 3GPP network elements (e.g., MME 202, HSS 204, BMSC 206,MTC-IWF 208, etc.) via secure policies (e.g. configured by the networkprovider) and APIs to the external and/or third party AS s and/orservice providers, for example, AS 1-AS M (wherein M is most anypositive integer) 210 ₁-210 _(M) that are within an AS pool. By doingso, the SCEF 102 allows the application providers to implement devicetriggering, device monitoring, and/or group message delivery for the IoTdevice, and/or to obtain status reports of the IoT devices' locationand/or network conditions on demand and subject to appropriate operatorspecific agreements in place. Moreover, using the APIs, the applicationproviders, AS 1-AS M 210 ₁-210 _(M), can access specific portions of thenetwork elements (e.g., MME/SGSN 202, HSS 204, BMSC 206, MTC-IWF 208,etc.) to extract specific information of their IoT devices and canpublish and/or provide targeted and intelligent services to the IoTdevices based on the extracted information.

The number of APIs that are to be generated against each of the networkelements (e.g., MME/SGSN 202, HSS 204, BMSC 206, MTC-IWF 208, etc.) withunique application layer protocols for dedicated signaling interfacesalong with their supported mandatory and optionally configurableinformation elements is substantially large, and the resulting protocolconversion per network element per interface makes the SCEF 102 acritical network element in the IoT/MTC network architecture. As eachnetwork element and its pooled configuration interfaces with a commonSCEF entity, the mobility network has a huge dependency on the SCEF 102.In an embodiment, the SCEF 102 employs (e.g., by utilizing the PAWcomponent 108) efficient protocol conversion schemes to expose theseinterfaces via generic and reconfigurable APIs in a protocol-independentmanner to AS 1-AS M 210 ₁-210 _(M).

As the IoT industry matures with the technological development andstandardization of a variety of IoT device models (e.g., 3GPP UEcategory types such as CAT1/CAT0/CATM and/or others with configurablefeatures via software upgrades) that support a multitude ofapplications, services across industry verticals, the resulting mobileconnectivity traffic model changes radically. The desire and demand toget these devices connected online creates a huge opportunity for themobile operators to drive innovative features into their networkelements such as the SCEF 102. With virtualization of existing mobilitynetwork functions and creation of new network functions, the SCEF 102has the onus of interworking with both physical and virtual networkfunctions to be able to expose signaling interfaces from each of theseunderlying physical/virtual networking entities to AS 1-AS M 210 ₁-210_(M) in a secure manner. The SCEF 102 employs a PAW function (e.g., viaPAW component 108) to provide intelligent, flexible, and dynamic networkarchitectures with integrated software defined policies that can helpboth network operators as well as service/application providers indelivering the best in class IoT infrastructure that is scalable,delivers superior end user quality of experience, and/or improves therevenue engine by creating new service models, thereby meeting andexceeding their business objectives. Moreover, the PAW function cancomprise a control system that takes as the input, “application layersignaling protocols” from its underlying physical/virtual networkelements (e.g., MME/SGSN 202, HSS 204, BMSC 206, MTC-IWF 208, etc.) thatare connected and delivers as the output, “generic set of APIs” that areinterface agnostic to the external application provider (e.g., AS 1-AS M210 ₁-210 _(M)). As an example, the external application provider inturn can use these APIs to perform on demand triggers for desired set ofIoT devices in a given geographic region, as well as request event basedconfiguration, reporting, status monitoring, deletion, new servicesrollout with an existing device or launch of new devices in specificlocations given the capabilities supported in the network.

Referring back to FIG. 2, there illustrated are network elements MME202, HSS 204, BMSC 206, and MTC-IWF 208 that are coupled to the SCEF 102via various interfaces like S6t, T6a, T6b etc. Developing and exposingan API for each of these various interfaces of the different networkelements can be very complex. Thus, the PAW function of SCEF 102 canconvert any of the interfaces into a unique and reconfigurable API, forexample, a standards based API (e.g., representational state transfer(REST)-based, open mobile alliance (OMA)-based, GSMA-based, etc.). Inone aspect, the API can be reconfigurable with intelligence within theSCEF 102, for example, on a per interface basis. Moreover, areconfigurable API is an API that is dynamically created (e.g.,on-the-fly, in real-time, etc.) by the SCEF 102 based on an analysis ofvarious parameters related to real-time traffic, such as, but notlimited to, amount of traffic received by the SCEF 102, type of trafficreceived by the SCEF 102, network element that is sending the traffic tothe SCEF 102, interface over which the SCEF 102 receives the traffic,etc. For example, the if there are 1 million IoT users trying to attachto MME 202 and they want to send information to AS 1 210 ₁ of anautomotive manufacturer on a first day, the SCEF 102 can utilize thisinformation and generate an API that will be configurable only as a T6aAPI (e.g., and not be configurable as a S6t or other non-T6a type API)that is employed by the MME 202. On a second day (or at another time),the SCEF 102 can configure the resources as another API, for example, aS6t API if determined that another application server AS M 210 _(M) istrying to extract subscription data from the HSS 204. Thus, in thisexample scenario, all the information coming in on S6t interface to theSCEF 102 can be spun out as an S6t API.

It is noted that the SCEF 102 can continuously monitor its resources andimplement mechanisms to avoid being saturated. In some example cases,more than one API can be generated (e.g., simultaneous or substantiallysimultaneous), for example, depending on demand and/or health conditionsof the SCEF 102. Further, the SCEF 102 can be a single vendor ormultiple vendor entity. The example scenario wherein the SCEF 102 ismultiple vendor entity can be more complicated and a network managementsystem 212 can be utilized to manage operations between the SCEF 102,network element(s) 104, and/or the AS(s) 106. The multi-vendor SCEF 102can communicate with a plurality of different vendors such as MMEvendors, SGSN vendors, and the like, and can generate different APIsthat are exposed to the application servers in a pool (e.g., AS 1-AS M(210 ₁-210 _(M))).

AS 1-AS M (210 ₁-210 _(M)) can comprise most any application serversdistributed over one or more industry segments; for example, IoTspecific servers, industrial servers, e-health servers, fleettransportation servers, shipping or mailing servers, automotive servers,and the like. The data requirements of the AS 1-AS M (210 ₁-210 _(M))are typically different based on the information that is to be leveragedfrom the 3GPP network. For example, an automotive manufacturer AS wouldlike to get updates on car readings on T6 interface since MME 202 wouldknow the location of the connected car. In this example scenario, the AScan send a trigger to the MME 202 via an API exposed by the SCEF 102 andthe MME 202 can respond with data over the T6a interface, which can beprovided to the AS by the SCEF 102 via an appropriate and dynamicallygenerated API.

Referring now to FIG. 3, there illustrated is an example system 300 fora policy-based dedicated interface to API exchange associated withcontrol-plane entities deployed in a pooled configuration, in accordancewith an aspect of the subject disclosure. In one example, MMEs canestablish diameter connections over a T6a interface towards apre-provisioned SCEF entity. In 3G networks, SGSNs can establishconnections towards the SCEF entity via a T6b interface. In a simplercore network design, the MME/SGSN network elements (segregated or acombined entity) can be directly connected to the SCEF entity whichfacilitates simpler connectivity as well as rapid exchange of theT6a/T6b diameter signaling transactions. However, larger operatorenvironments can comprise several regional pools of control planeentities, for example, MME/SGSN pool 302 that has N entities-MME/SGSN304 ₁-304 _(N) (where N is most any natural number greater than 1) in asingle pooled configuration. Each MME/SGSN pool 302 can be served bymore than one SCEF entity, for example, SCEF 1 306 ₁ and SCEF 2 306 ₂that address the traffic demands emanating from the massive number ofIoT devices in a given wider geographic region served by the MME/SGSNpool 302. It is noted that SCEF 1 306 ₁ and SCEF 2 306 ₂ can besubstantially similar to SCEF 102 and can comprise functionality as morefully described herein, for example, as described above with regard toSCEF 102. In one aspect, SCEF 1 306 ₁ can operate in an active modewhile SCEF 2 306 ₂ can be in a standby mode. At most any time, forexample, periodically and/or in response to an event, the operatingmodes of the SCEF 1 306 ₁ and SCEF 2 306 ₂ can be switched, such thatSCEF 2 306 ₂ can operate in an active mode while SCEF 1 306 ₁ can be ina standby mode. During the active mode, the SCEF can dynamicallygenerate and expose reconfigurable APIs for traffic received from theMME/SGSN pool 302. In an alternative aspect, both SCEFs, SCEF 1 306 ₁and SCEF 2 306 ₂ can simultaneously operate in the active mode andimplement load sharing to efficiently handle the traffic received fromthe MME/SGSN pool 302.

It is noted that the MME/SGSN 304 ₁-304 _(N) can be substantiallysimilar to MME/SGSN 202 and can comprise functionality as more fullydescribed herein, for example, as described above with regard toMME/SGSN 202. Further, it is noted that the AS(s) 106 and the networkmanagement system 212 can comprise functionality as more fully describedherein, for example, as described above with regard to systems 100-200.Additionally, although system 300 is described with respect to a LTEnetwork, it is noted that the subject disclosure is not limited to LTEnetworks and can be utilized in most any communication network.

Referring now to FIG. 4, there illustrated is an example system 400 forproviding redundancy during policy-based API generation, according to anaspect of the subject disclosure. It is noted that the AS(s) 106, AS1-AS M (210 ₁-210 _(M)), network management system 212, MME/SGSN pool302, MME/SGSN 304 ₁-304 _(N), SCEF 1 306 ₁, and SCEF 2 306 ₂ cancomprise functionality as more fully described herein, for example, asdescribed above with regard to systems 100-300. In one embodiment, oneor more additional sets of SCEFs, for example, SCEF 1 402 ₁ and SCEF 2402 ₂ can be deployed in geo-redundant data centers (404, 406), forexample, to account for disaster recovery. In an example scenariowherein SCEF 1 306 ₁ and/or SCEF 2 306 ₂ fail (and/or cannot perform atpredefined performance thresholds), SCEF 1 402 ₁ and SCEF 2 402 ₂ can beactivated and can handle all or portions of traffic from the MME/SGSNpool 302. In such complex networking scenarios, the MME/SGSN 304 ₁-304_(N) can conduct domain name system (DNS) procedures to select theclosest SCEF entities (e.g., from SCEF 1 306 ₁, SCEF 2 306 ₂, SCEF 1 402₁, and/or SCEF 2 402 ₂) to complete signaling transactions. Althoughonly one set of additional SCEFs (e.g., SCEF 1 402 ₁, and/or SCEF 2 402₂) are depicted, it is noted that the subject disclosure is not solimited and that more than one set of SCEFs can be deployed to provideadditional geo-redundancy.

In one aspect, the network management system 212 can be used as apolicy-based mapping engine that instructs the SCEFs (e.g., SCEF 1 306₁, SCEF 2 306 ₂, SCEF 1 402 ₁, and/or SCEF 2 402 ₂) to accept theinterface traffic from the MME/SGSN pool 302 and steer it to the AS pool106. In case of error conditions, for example, failover conditions, thenetwork management system 212 is tightly coupled to its nodes to steer aspecific API to the AS pool 106.

FIG. 5 illustrates an example system 500 that facilitates routing of IoTroaming traffic via SCEF interworking, according to aspects of thedisclosed subject matter. In one aspect, the SCEF entity in the networkhandling home public land mobile network (PLMN) IoT users/devices canalso support handling the IoT users/devices from a roaming partner.Large carrier networks typically have few hundreds of global roamingpartners and the SCEF in the visited network for a roaming device is toeffectively interwork with the SCEF in their home network to meet thedemands of their home application/service providers while they areroaming outside of their home network. In a similar manner, when thehome PLMN IoT users/devices roam outbound into their partnered roamingcarrier, comparable service level behaviors based on applications can beprovided on-demand when trying to establish connectivity and/or datatraffic exchange with their home service providers. A standards basedhome routed network architecture design model depicted in FIG. 5 can beleveraged so that IoT devices get the same level of experience when theyare in their home PLMN or while roaming in other networks.

Roaming IoT devices can couple to a visitor MME within an MME pool, forexample, MME pool A 502 a and/or MME pool B 502 b. The visitor MME cansteer the IoT traffic to an interworking (IWK) SCEF function, forexample, IWK SCEF 1-4 504 ₁-504 ₈. In one aspect, the IWK SCEF 1-4 504₁-504 ₈ can interfaces to the home SCEFs for example, SECF 1-2 506 ₁-506₄. In one example, the T6a traffic received from the visitor MME can beforwarded to the home SCEFs (e.g., SCEF 1-2 506 ₁-506 ₄) via a T7diameter interface through the inter exchange carrier (IXC)/IP packetexchange (IPX) 508 ₁-508 ₂. According to an embodiment, the IWK SCEF 1-4504 ₁-504 ₈ can be substantially similar to and comprise functionalityas more fully described herein, for example, as described herein withrespect to SCEF 102. For its home PLMN devices, the IWK SCEF 1-4 504₁-504 ₈ can operate same as (or substantially similar to) the SCEF 102by employing a PAW functionality to generate and expose interfaceagnostic APIs to external providers. For visitor devices, the IWK SCEF1-4 504 ₁-504 ₈ can act as a relay point that forwards the traffic onthe T7 interface to a home SCEF, for example, SCEF 1-2 506 ₁-506 ₄,which in turn perform the protocol agnostic wrapping and interfaceagnostic API exposition. It is noted that IWK SCEF functions (e.g.,forwarding of received data) and regular SCEF functions (e.g.,generation and exposition of APIs) can be implemented by same deviceand/or multiple devices, for example, independent virtual machines in acloud architecture.

Although only two home and visitor networks are depicted in FIG. 5, itis noted that the subject disclosure is not that limited and greater orfewer number of networks can be implemented. It is noted that the MMEpool A 502 a and/or MME pool B 502 b can be substantially similar toMME/SGSN pool 302 and can comprise functionality as more fully describedherein, for example, as described above with regard to MME/SGSN pool302. Further, the SCEF 1-2 506 ₁-506 ₄ can be substantially similar toSCEF 102 and comprise functionality as more fully described herein, forexample, as described above with regard to SCEF 102. Furthermore, ASpool A 510 a and AS pool B 510 b can be substantially similar to AS pool106 and comprise functionality as more fully described herein, forexample, as described above with regard to AS pool 106. Additionally,the network managements systems-visitor network management system 512₁-512 ₂ and home network management system 514 ₁-514 ₂ can besubstantially similar to network management system 212 and comprisefunctionality as more fully described herein, for example, as describedabove with regard to network management system 212. As an example, thenetwork management systems can be centrally controlled.

FIG. 6 illustrates an example system 600 that comprises an SCEF 102integrated with a data analytics engine (DAE) 602 in accordance with thesubject disclosure. The DAE 602 can work closely in conjunction with thePAW component 108 to facilitate tracking a specific set ofoperator-defined metrics that are associated with the application layerprotocols being exposed from specific network elements (202-208). It isnoted that the SCEF 102, AS pool 106, PAW component 108, MME/SGSN 202,HSS 204, BMSC 206, MTC-IWF 208, AS 1-M 210 ₁-210 _(M), and networkmanagement system 212 can comprise functionality as more fully describedherein, for example, as described above with regard to systems 100-400.

In one aspect, the DAE 602 can expose specific set of metrics tospecific set of industry verticals. For example, an automotive AS canrequest data representing IoT devices' geographical location, ane-health AS can request specific health related info from the IoTdevices, etc. Moreover, the AS 1-M 210 ₁-210 _(M) can utilize the DAE602 to extract more refined information from a specific network element.The DAE 602 can provide the information as an on-demand API, forexample, by employing the PAW component 108. In one embodiment, the DAE602 can communicate with the network management system 212 to extractthe configuration of the network elements (e.g., 202-208), theirinterface as well as protocol states towards the SCEF 102 and ensurethat the exposed APIs and analytics in real-time truly reflect thenetwork entities that are available on-demand for access by a givenapplication provider. The application provider in turn can use theseAPIs to be able to perform on demand triggers for desired set of IoTdevices in a given geographic region, as well as request event basedconfiguration, reporting, status monitoring, deletion, new servicesrollout with an existing device, and/or launch of new devices inspecific locations given the capabilities supported in the network.Further, a closed loop feedback system 604 can be utilized within eachof the independent network elements (e.g., 202-208) to enable the SCEF102 to intelligently control the traffic from the network elements in amanner such that the SCEF 102 does not get saturated and can expose theAPIs in a timely manner.

Referring now to FIG. 7, there illustrated is an example system 700 thatemploys an artificial intelligence (AI) component (702) to facilitateautomating one or more features in accordance with the subjectembodiments. It can be noted that the SCEF 102, PAW component 108, andDAE 602 can comprise functionality as more fully described herein, forexample, as described above with regard to systems 100-600.

In an example embodiment, system 700 (e.g., in connection withautomatically developing and/or exposing APIs) can employ variousAI-based schemes (e.g., intelligent processing/analysis, machinelearning, etc.) for carrying out various aspects thereof. For example, aprocess for determining which APIs to expose, determining optimal APIsfor specific type of traffic, determining metrics that are to betracked, etc. can be facilitated via an automatic classifier systemimplemented by AI component 702. Moreover, the AI component 702 canvarious exploit artificial intelligence (AI) methods or machine learningmethods. Artificial intelligence techniques can typically apply advancedmathematical algorithms—e.g., decision trees, neural networks,regression analysis, principal component analysis (PCA) for feature andpattern extraction, cluster analysis, genetic algorithm, or reinforcedlearning—to a data set. In particular, AI component 702 can employ oneof numerous methodologies for learning from data and then drawinginferences from the models so constructed. For example, Hidden MarkovModels (HMMs) and related prototypical dependency models can beemployed. General probabilistic graphical models, such asDempster-Shafer networks and Bayesian networks like those created bystructure search using a Bayesian model score or approximation can alsobe utilized. In addition, linear classifiers, such as support vectormachines (SVMs), non-linear classifiers like methods referred to as“neural network” methodologies, fuzzy logic methodologies can also beemployed.

As will be readily appreciated from the subject specification, anexample embodiment can employ classifiers that are explicitly trained(e.g., via a generic training data) as well as implicitly trained (e.g.,via observing device/operator preferences, historical information,receiving extrinsic information, type of service, type of device, etc.).For example, SVMs can be configured via a learning or training phasewithin a classifier constructor and feature selection module. Thus, theclassifier(s) of AI component 702 can be used to automatically learn andperform a number of functions, comprising but not limited to determiningaccording to a predetermined criteria, protocol agnostic APIs that areto be exposed, metrics that are associated with the application layerprotocols being exposed from network elements, etc. The criteria cancomprise, but is not limited to, historical patterns and/or trends,network operator preferences and/or policies, application/serviceprovider preferences, predicted traffic flows, event data, latency data,reliability/availability data, current time/date, and the like.

According to an embodiment, the network architecture disclosed hereinprovides several non-limiting advantages and features such as, but notlimited to, (i) maintaining technology leadership and competitive edgein the IoT eco-system for disruptive applications/services delivery overthe world class mobility infrastructure; (ii) providing a common SCEFentity towards the network elements in the mobility core network thatprovides intelligent and/or flexible connectivity to thephysical/virtual core network elements; (iii) providing a common SCEFentity acting as a gateway access to the external application and/orservice provider community via operator defined set of APIs exposedsecurely; (iv) providing an integrated SCEF analytics capability (e.g.,via the DAE 602) that provides value added and event based services tothe external providers for targeted IoT devices and network analytics ondemand; (v) utilizing the analytics information to develop new servicesand create new revenue sources that mutually benefit infrastructure andapplication providers; (vi) providing a robust interworking of SCEF withits peer network entities and application providers to complete highvolume IoT transactions in a cost-effective manner; (vii) maintaining asuperior customer experience across IoT industry verticals that leveragebest in class LTE based mobility network infrastructure; (viii)supporting global IoT roaming with efficient SCEF interworking to createeffortless connectivity and enhance the overall user experience; (ix)successfully managing growth resulting from explosion of IoT devicevolumes via dynamic network reconfiguration, expansion via virtualnetworking functions, roll out of new services and business models; (x)leveraging distributed and/or pooled SCEF architecture designs forintelligent application layer protocol conversions and securely expose aconfigurable set of APIs to third party providers; (xi) proactive andintelligent monitoring inherent in SCEF for potential failure detectionand/or dynamic re-routing of the APIs to minimize network failureconditions and external provider's on-demand access to the networkresources; etc.

FIGS. 8-9 illustrate flow diagrams and/or methods in accordance with thedisclosed subject matter. For simplicity of explanation, the flowdiagrams and/or methods are depicted and described as a series of acts.It is to be understood and noted that the various embodiments are notlimited by the acts illustrated and/or by the order of acts, for exampleacts can occur in various orders and/or concurrently, and with otheracts not presented and described herein. Furthermore, not allillustrated acts may be required to implement the flow diagrams and/ormethods in accordance with the disclosed subject matter. In addition,those skilled in the art will understand and note that the methods couldalternatively be represented as a series of interrelated states via astate diagram or events. Additionally, it should be further noted thatthe methods disclosed hereinafter and throughout this specification arecapable of being stored on an article of manufacture to facilitatetransporting and transferring such methods to computers. The termarticle of manufacture, as used herein, is intended to encompass acomputer program accessible from any computer-readable device orcomputer-readable storage/communications media.

Referring now to FIG. 8 there illustrated is an example method 800 thatfacilitates protocol agnostic wrapping of traffic associated with IoTdevices during API generation, according to an aspect of the subjectdisclosure. In an aspect, method 800 can be implemented by one or morenetwork devices (e.g., SECF 102) of a communication network (e.g.,cellular network). Telecommunication equipment manufacturers aredeveloping advanced wireless networking products with innovativesoftware feature capabilities as plug-ins and/or configurable APIs fordistribution to third party vendors, applications, and/or serviceproviders accessing such APIs exposed by the carriers can mutuallybenefit from such advanced networking solutions. Network carriers candifferentiate their IoT services offering by providing unique valueadditions in securely exposing a generic set of APIs that can offerevent based monitoring, reporting, and/or triggering mechanisms forglobal IoT service providers who in turn can use such useful data fromoperators to spin new services and/or create revenues that benefit bothworlds. Moreover, global wireless operators as well as applicationsand/or services providers in the IoT industry benefit from each otherwith the intelligent access capabilities made available by the mobilitynetwork elements.

At 802, IoT traffic can be received from a network element (e.g.,MME/SGSN, HSS, BMSC, MTC-IWF, etc.) via a standard interface (e.g.,diameter interface). At 804, a protocol agnostic wrapper function can beutilized to generate a reconfigurable API. Further, at 806, thereconfigurable API can be exposed to one or more third party applicationproviders. Moreover, network carriers can expose APIs associated withtheir network elements signaling interfaces to external applicationsand/or service providers with suitable agreements in place therebyenabling custom APIs using open source tools to create new portalsand/or services. Such a model can create a truly globally connectedworld where users can leverage best in class mobility networkinfrastructure to get connected, come online, collaborate and/or sharevia social network evolution in turn creating new service and revenueopportunities.

FIG. 9 illustrates an example method 900 that facilitates integratingdata analytics capabilities in a SCEF, according to an aspect of thesubject disclosure. As an example, method 900 can be implemented by oneor more network devices (e.g., SCEF 102) of a communication network(e.g., cellular network). Service providers can establish locationspecific IoT device triggers and/or monitoring with a desired level ofaccuracy, collect raw data, extract analytics associated with theirfunctional and operational aspects in the network that could in turn beused to develop intelligent business metrics, innovate revenuegeneration model from data analytics, and/or streamline operations aswell as location based targeted consumer services where appropriate.Integrated SCEF data analytics capability provides value-added and/orevent-based services to the external providers for targeted IoT devicesand network analytics on demand.

At 902, operator-defined metrics that are associated with applicationlayer protocols exposed from one or more network elements (e.g.,MME/SGSN, HSS, BMSC, MTC-IWF, etc.) can be tracked. Further, at 904, theoperator-defined metrics can be exposed to a specific set of industryverticals. As an example, the operator-defined metrics can be utilizedto develop new services and/or create new revenue sources that mutuallybenefit carrier infrastructure and application providers.

FIG. 10 illustrates a high-level block diagram that depicts an exampleLTE network architecture 1000 that can employ the disclosedcommunication architecture. In one aspect, network architecture 1000 cancomprise at least a portion of systems 100-600. The evolved RAN for LTEconsists of an eNodeB (eNB) 1002 that can facilitate connection of MS1004 to an evolved packet core (EPC) network. In one aspect, the MS 1004is physical equipment or Mobile Equipment (ME), such as a mobile phoneor a laptop computer that is used by mobile subscribers, with aSubscriber identity Module (SIM). The SIM comprises an InternationalMobile Subscriber Identity (IMSI) and/or MSISDN, which is a uniqueidentifier of a subscriber. The MS 1004 comprises an embedded clientthat receives and processes messages received by the MS 1004. As anexample, the embedded client can be implemented in JAVA.

The connection of the MS 1004 to the evolved packet core (EPC) networkis subsequent to an authentication, for example, a SIM-basedauthentication between the MS 1004 and the evolved packet core (EPC)network. In one aspect, the MME 1006 provides authentication of the MS1004 by interacting with the Home Subscriber Server (HSS) 1008 via aGateway Mobile Location Centre (GMLC) 1010. The GMLC 1010 can requestrouting information from the HSS 1008. The HSS 1008 contains asubscriber profile and keeps track of which core network node iscurrently handling the subscriber. It also supports subscriberauthentication and authorization functions (AAA). In networks with morethan one HSS 1008, a subscriber location function provides informationon the HSS 1008 that contains the profile of a given subscriber. In oneaspect, this authentication can be utilized to secure population of theuser/device profile data by a primary user. Further, the MME 1006 can becoupled to an enhanced Serving Mobile Location Center (E-SMLC) 1012supports location services (LCS) and coordinates positioning of the MS1004. The MS 1004 and the E-SMLC can communicate using an LTEPositioning Protocol (LPP) and/or LPP extensions (LPPe)

As an example, the eNB 1002 can host a PHYsical (PHY), Medium AccessControl (MAC), Radio Link Control (RLC), and Packet Data ControlProtocol (PDCP) layers that comprise the functionality of user-planeheader-compression and encryption. In addition, the eNB 1002 canimplement at least in part Radio Resource Control (RRC) functionality(e.g., radio resource management, admission control, scheduling, cellinformation broadcast, etc.). The eNB 1002 can be coupled to a servinggateway (SGW) 1014 that facilitates routing of user data packets andserves as a local mobility anchor for data bearers when the MS 1004moves between eNBs. The SGW 1014 can act as an anchor for mobilitybetween LTE and other 3GPP technologies (GPRS, UMTS, etc.). When MS 1004is in an idle state, the SGW 1014 terminates a downlink (DL) data pathand triggers paging when DL data arrives for the MS 1004. Further, theSGW 1014 can perform various administrative functions in the visitednetwork such as collecting information for charging and lawfulinterception. In one aspect, the SGW 1014 can be coupled to a PacketData Network Gateway (PDN GW) 1016 that provides connectivity betweenthe MS 1004 and external packet data networks such as IPservice(s)/network(s) 1024 via the IP Multimedia Subsystem (IMS) network1026. Moreover, the PDN GW 1016 is a point of exit and entry of trafficfor the MS 1004. It is noted that the MS 1004 can have simultaneousconnectivity with more than one PDN GW (not shown) for accessingmultiple PDNs.

The PDN GW 1016 performs IP address allocation for the MS 1004, as wellas QoS enforcement and implements flow-based charging according to rulesfrom a Policy Control and Charging Rules Function (PCRF) 1018. The PCRF1018 can facilitate policy control decision-making and controlflow-based charging functionalities in a Policy Control EnforcementFunction (PCEF), which resides in the PDN GW 1016. The PCRF 1018 canstore data (e.g., QoS class identifier and/or bit rates) thatfacilitates QoS authorization of data flows within the PCEF. In oneaspect, the PDN GW 1016 can facilitate filtering of downlink user IPpackets into the different QoS-based bearers and perform policyenforcement, packet filtering for each user, charging support, lawfulinterception and packet screening. Further, the PDN GW 1016 acts as theanchor for mobility between 3GPP and non-3GPP technologies such as WiMAXand 3GPP2 (CDMA 1× and EvDO). An Evolved Packet Data Gateway (ePDG) 1020is employed for communications between the EPC and untrusted non-3GPPnetworks that require secure access, such as a Wi-Fi, LTE metro, andfemtocell access networks, for example served by access point 1022.

Although an LTE network architecture 1000 is described and illustratedherein, it is noted that most any communication network architecture canbe utilized to implement the disclosed embodiments.

Referring now to FIG. 11, there is illustrated a block diagram of acomputer 1102 operable to execute the disclosed communicationarchitecture. In order to provide additional context for various aspectsof the disclosed subject matter, FIG. 11 and the following discussionare intended to provide a brief, general description of a suitablecomputing environment 1100 in which the various aspects of thespecification can be implemented. While the specification has beendescribed above in the general context of computer-executableinstructions that can run on one or more computers, those skilled in theart will recognize that the specification also can be implemented incombination with other program modules and/or as a combination ofhardware and software.

Generally, program modules comprise routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will note thatthe inventive methods can be practiced with other computer systemconfigurations, comprising single-processor or multiprocessor computersystems, minicomputers, mainframe computers, as well as personalcomputers, hand-held computing devices, microprocessor-based orprogrammable consumer electronics, and the like, each of which can beoperatively coupled to one or more associated devices.

The illustrated aspects of the specification can also be practiced indistributed computing environments where certain tasks are performed byremote processing devices that are linked through a communicationsnetwork. In a distributed computing environment, program modules can belocated in both local and remote memory storage devices.

Computing devices typically comprise a variety of media, which cancomprise computer-readable storage media and/or communications media,which two terms are used herein differently from one another as follows.Computer-readable storage media can be any available storage media thatcan be accessed by the computer and comprises both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media cancomprise, but are not limited to, RAM, ROM, EEPROM, flash memory orother memory technology, CD-ROM, digital versatile disk (DVD) or otheroptical disk storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or other tangible and/ornon-transitory media which can be used to store desired information.Computer-readable storage media can be accessed by one or more local orremote computing devices, e.g., via access requests, queries or otherdata retrieval protocols, for a variety of operations with respect tothe information stored by the medium.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and comprises any informationdelivery or transport media. The term “modulated data signal” or signalsrefers to a signal that has one or more of its characteristics set orchanged in such a manner as to encode information in one or moresignals. By way of example, and not limitation, communication mediacomprise wired media, such as a wired network or direct-wiredconnection, and wireless media such as acoustic, radio frequency (RF),infrared and other wireless media.

With reference again to FIG. 11, the example environment 1100 forimplementing various aspects of the specification comprises a computer1102, the computer 1102 comprising a processing unit 1104, a systemmemory 1106 and a system bus 1108. As an example, the component(s),application(s) server(s), equipment, system(s), interface(s),gateway(s), controller(s), node(s), engine(s), entity(ies), function(s)and/or device(s) (e.g., SCEF 102, control plane entity(ies) 104, ASs106, PAW component 108, MME/SGSN 202, HSS, 204, BMSC 206, MTC-IWF 208,AS 1-AS M 210 ₁-210 _(M), network management system 212, MME/SGSN pool302, MMEs 304 ₁-30 _(M), SCEF 1-2 306 ₁-306 ₂, SCEF 1-2 402 ₁-402 ₂, MMEpool A 502 a, MME pool B 502 b, IWK SCEF 1-4 504 ₁-504 ₈, SCEF 1-25061-5064, AS pool A 510 a, AS pool B 510 b, visitor network managementsystem 5121-5122, home network management system 5141-5142, DAE 602,feedback system 604, AI component 702, ENB 1002, MS 1004, MME 1006, HSS1008, GMLC 101, E-SMLC 1012, SGW 1014, PDN GW 1016, PCRF 1018, IPservice/networks 1024, IMS network 1026, etc.) disclosed herein withrespect to systems 100-700 and 1000 can each comprise at least a portionof the computer 1102. The system bus 1108 couples system componentscomprising, but not limited to, the system memory 1106 to the processingunit 1104. The processing unit 1104 can be any of various commerciallyavailable processors. Dual microprocessors and other multi-processorarchitectures can also be employed as the processing unit 1104.

The system bus 1108 can be any of several types of bus structure thatcan further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 1106comprises read-only memory (ROM) 1110 and random access memory (RAM)1112. A basic input/output system (BIOS) is stored in a non-volatilememory 1110 such as ROM, EPROM, EEPROM, which BIOS contains the basicroutines that help to transfer information between elements within thecomputer 1102, such as during startup. The RAM 1112 can also comprise ahigh-speed RAM such as static RAM for caching data.

The computer 1102 further comprises an internal hard disk drive (HDD)1114, which internal hard disk drive 1114 can also be configured forexternal use in a suitable chassis (not shown), a magnetic floppy diskdrive (FDD) 1116, (e.g., to read from or write to a removable diskette1118) and an optical disk drive 1120, (e.g., reading a CD-ROM disk 1122or, to read from or write to other high capacity optical media such asthe DVD). The hard disk drive 1114, magnetic disk drive 1116 and opticaldisk drive 1120 can be connected to the system bus 1108 by a hard diskdrive interface 1124, a magnetic disk drive interface 1126 and anoptical drive interface 1128, respectively. The interface 1124 forexternal drive implementations comprises at least one or both ofUniversal Serial Bus (USB) and IEEE 1394 interface technologies. Otherexternal drive connection technologies are within contemplation of thesubject disclosure.

The drives and their associated computer-readable storage media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 1102, the drives andstorage media accommodate the storage of any data in a suitable digitalformat. Although the description of computer-readable storage mediaabove refers to a HDD, a removable magnetic diskette, and a removableoptical media such as a CD or DVD, it should be noted by those skilledin the art that other types of storage media which are readable by acomputer, such as zip drives, magnetic cassettes, flash memory cards,solid-state disks (SSD), cartridges, and the like, can also be used inthe example operating environment, and further, that any such storagemedia can contain computer-executable instructions for performing themethods of the specification.

A number of program modules can be stored in the drives and RAM 1112,comprising an operating system 1130, one or more application programs1132, other program modules 1134 and program data 1136. All or portionsof the operating system, applications, modules, and/or data can also becached in the RAM 1112. It is noted that the specification can beimplemented with various commercially available operating systems orcombinations of operating systems.

A user can enter commands and information into the computer 1102 throughone or more wired/wireless input devices, e.g., a keyboard 1138 and/or apointing device, such as a mouse 1140 or a touchscreen or touchpad (notillustrated). These and other input devices are often connected to theprocessing unit 1104 through an input device interface 1142 that iscoupled to the system bus 1108, but can be connected by otherinterfaces, such as a parallel port, an IEEE 1394 serial port, a gameport, a USB port, an IR interface, etc. A monitor 1144 or other type ofdisplay device is also connected to the system bus 1108 via aninterface, such as a video adapter 1146.

The computer 1102 can operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 1148. The remotecomputer(s) 1148 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentappliance, a peer device or other common network node, and typicallycomprises many or all of the elements described relative to the computer1102, although, for purposes of brevity, only a memory/storage device1150 is illustrated. The logical connections depicted comprisewired/wireless connectivity to a local area network (LAN) 1152 and/orlarger networks, e.g., a wide area network (WAN) 1154. Such LAN and WANnetworking environments are commonplace in offices and companies, andfacilitate enterprise-wide computer networks, such as intranets, all ofwhich can connect to a global communications network, e.g., theInternet.

When used in a LAN networking environment, the computer 1102 isconnected to the local network 1152 through a wired and/or wirelesscommunication network interface or adapter 1156. The adapter 1156 canfacilitate wired or wireless communication to the LAN 1152, which canalso comprise a wireless access point disposed thereon for communicatingwith the wireless adapter 1156.

When used in a WAN networking environment, the computer 1102 cancomprise a modem 1158, or is connected to a communications server on theWAN 1154, or has other means for establishing communications over theWAN 1154, such as by way of the Internet. The modem 1158, which can beinternal or external and a wired or wireless device, is connected to thesystem bus 1108 via the serial port interface 1142. In a networkedenvironment, program modules depicted relative to the computer 1102, orportions thereof, can be stored in the remote memory/storage device1150. It will be noted that the network connections shown are exampleand other means of establishing a communications link between thecomputers can be used.

The computer 1102 is operable to communicate with any wireless devicesor entities operatively disposed in wireless communication, e.g.,desktop and/or portable computer, server, communications satellite, etc.This comprises at least Wi-Fi and Bluetooth™ wireless technologies orother communication technologies. Thus, the communication can be apredefined structure as with a conventional network or simply an ad hoccommunication between at least two devices.

Wi-Fi, or Wireless Fidelity networks use radio technologies called IEEE802.11 (a, b, g, n, etc.) to provide secure, reliable, fast wirelessconnectivity. A Wi-Fi network can be used to connect computers to eachother, to the Internet, and to wired networks (which use IEEE 802.3 orEthernet). Wi-Fi networks operate in the unlicensed 2.4 and 5 GHz radiobands, at an 11 Mbps (802.11a) or 54 Mbps (802.11b) data rate, forexample, or with products that contain both bands (dual band), so thenetworks can provide real-world performance similar to the basic 10BaseTwired Ethernet networks used in many offices.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor may also be implemented as acombination of computing processing units.

In the subject specification, terms such as “data store,” data storage,”“database,” “cache,” and substantially any other information storagecomponent relevant to operation and functionality of a component, referto “memory components,” or entities embodied in a “memory” or componentscomprising the memory. It will be noted that the memory components, orcomputer-readable storage media, described herein can be either volatilememory or nonvolatile memory, or can comprise both volatile andnonvolatile memory. By way of illustration, and not limitation,nonvolatile memory can comprise read only memory (ROM), programmable ROM(PROM), electrically programmable ROM (EPROM), electrically erasable ROM(EEPROM), or flash memory. Volatile memory can comprise random accessmemory (RAM), which acts as external cache memory. By way ofillustration and not limitation, RAM is available in many forms such assynchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM),double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), SynchlinkDRAM (SLDRAM), and direct Rambus RAM (DRRAM). Additionally, thedisclosed memory components of systems or methods herein are intended tocomprise, without being limited to comprising, these and any othersuitable types of memory.

Referring now to FIG. 12, there is illustrated a schematic block diagramof a computing environment 1200 in accordance with the subjectspecification. The system 1200 comprises one or more client(s) 1202. Theclient(s) 1202 can be hardware and/or software (e.g., threads,processes, computing devices).

The system 1200 also comprises one or more server(s) 1204. The server(s)1204 can also be hardware and/or software (e.g., threads, processes,computing devices). The servers 1204 can house threads to performtransformations by employing the specification, for example. Onepossible communication between a client 1202 and a server 1204 can be inthe form of a data packet adapted to be transmitted between two or morecomputer processes. The data packet may comprise a cookie and/orassociated contextual information, for example. The system 1200comprises a communication framework 1206 (e.g., a global communicationnetwork such as the Internet, cellular network, etc.) that can beemployed to facilitate communications between the client(s) 1202 and theserver(s) 1204.

Communications can be facilitated via a wired (comprising optical fiber)and/or wireless technology. The client(s) 1202 are operatively connectedto one or more client data store(s) 1208 that can be employed to storeinformation local to the client(s) 1202 (e.g., cookie(s) and/orassociated contextual information). Similarly, the server(s) 1204 areoperatively connected to one or more server data store(s) 1210 that canbe employed to store information local to the servers 1204.

What has been described above comprises examples of the presentspecification. It is, of course, not possible to describe everyconceivable combination of components or methods for purposes ofdescribing the present specification, but one of ordinary skill in theart may recognize that many further combinations and permutations of thepresent specification are possible. Accordingly, the presentspecification is intended to embrace all such alterations, modificationsand variations that fall within the spirit and scope of the appendedclaims. Furthermore, to the extent that the term “comprises” is used ineither the detailed description or the claims, such term is intended tobe inclusive in a manner similar to the term “comprising” as“comprising” is interpreted when employed as a transitional word in aclaim.

What is claimed is:
 1. A system, comprising: a processor; and a memorythat stores executable instructions that, when executed by theprocessor, facilitate performance of operations, comprising: determininga configurable application programming interface that is employable toexpose a control plane device of a communication network to athird-party application server device that is external to thecommunication network; and based on the configurable applicationprogramming interface, facilitating a communication of user equipmentdata, associated with a user equipment served by the control planedevice, from the control plane device to the third-party applicationserver device, wherein the user equipment data is employable todetermine a targeted service that is to be provided to the userequipment.
 2. The system of claim 1, wherein the user equipmentcomprises a machine-to-machine device.
 3. The system of claim 1, whereinthe targeted service comprises a device triggering service that providesa trigger to the user equipment.
 4. The system of claim 1, wherein thetargeted service comprises a device monitoring service that tracksparameters associated with the user equipment.
 5. The system of claim 1,wherein the configurable application programming interface is a protocolagnostic application programming interface.
 6. The system of claim 1,wherein the determining the configurable application programminginterface comprises determining the configurable application programminginterface based on a translation of application layer protocols.
 7. Thesystem of claim 1, wherein the configurable application programminginterface is employable to expose the control plane device based onpolicy data indicative of a security policy associated with thecommunication network.
 8. The system of claim 1, wherein the determiningthe configurable application programming interface comprises determiningthe configurable application programming interface based on networktraffic data.
 9. The system of claim 1, wherein the determining theconfigurable application programming interface comprises determining theconfigurable application programming interface based on interface dataassociated with an industry-defined interface utilized by the controlplane device.
 10. The system of claim 1, wherein the configurableapplication programming interface comprises a first configurableapplication programming interface that is utilized to expose the controlplane device to the third-party application server device during a firsttime period, and wherein the operations further comprise: during asecond time period, determining a second configurable applicationprogramming interface that is employable to expose the control planedevice to the third-party application server device.
 11. A method,comprising: determining, by a gateway device comprising a processor, aconfigurable application programming interface that is employable toexpose a control plane device of a communication network to athird-party application server device that is external to thecommunication network; and based on the configurable applicationprogramming interface, facilitating, by the gateway device, a transferof information, associated with a user equipment served by the controlplane device, between the control plane device and the third-partyapplication server device, wherein the information is to be utilized toestablish a targeted service associated with the user equipment.
 12. Themethod of claim 11, wherein the determining comprises determining aprotocol-independent application programming interface.
 13. The methodof claim 11, wherein the configurable application programming interfaceis a first configurable application programming interface and the methodfurther comprises: reconfiguring, by the gateway device, the firstconfigurable application programming interface to generate a secondconfigurable application programming interface that is employable toexpose the control plane device to the third-party application serverdevice.
 14. The method of claim 13, wherein the reconfiguring comprisesreconfiguring the first configurable application programming interfacebased on network traffic data.
 15. The method of claim 13, wherein thereconfiguring comprises reconfiguring the first configurable applicationprogramming interface based on determining a change in an amount of datareceived from the control plane device.
 16. The method of claim 13,wherein the reconfiguring comprises reconfiguring the first configurableapplication programming interface based on determining a change in atype of data received from the control plane device.
 17. Amachine-readable storage medium, comprising executable instructionsthat, when executed by a processor, facilitate performance ofoperations, comprising: configuring a protocol-agnostic applicationprogramming interface that is employable to expose a control planedevice of a communication network to a third-party application serverdevice that is external to the communication network; and facilitating,via the protocol-agnostic application programming interface, a transferof information, associated with a user equipment served by the controlplane device, between the control plane device and the third-partyapplication server device, wherein the transfer facilitates animplementation of a targeted service associated with the user equipment.18. The machine-readable storage medium of claim 17, wherein the userequipment comprises an Internet of thing device.
 19. Themachine-readable storage medium of claim 17, wherein the configuringcomprises configuring the protocol-agnostic application programminginterface based on network traffic data.
 20. The machine-readablestorage medium of claim 17, wherein the configuring comprisesconfiguring the protocol-agnostic application programming interfacebased on type data indicative of a type of the control plane device.